Well prog execution facilitation system and method

ABSTRACT

A prog analysis and execution system and method. The system includes a computer control system, an interface engine in communication with the computer control system, the interface engine being configured to receive prog information, and an action item development engine in communication with the control system, the action item development engine being configured to analyze received prog information and to determine corresponding action items. The system further includes a sensor engine in communication with the computer control system, the sensor engine being configured to receive input from at least one sensor for use in controlling a well drilling operation, and an operational equipment engine in communication with the computer control system, the operational equipment engine being configured to receive input from the computer control system and to control the well drilling operation in accordance with the determined action items in the prog.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation of co-pending U.S. application Ser. No.11/747,110 (U.S. Patent Publication No. 2008-0281525 A1), filed May 10,2007, the contents of which is hereby incorporated herein in itsentirety by express reference thereto.

BACKGROUND

A well prognosis (prog) is generally understood in the drilling industryto be a detailed and lengthy document containing specifications, goals,plans, etc. for drilling and completing a well, and most drillingcompanies have a preferred format and structure for their progs.However, there is no universal standardization for progs, and thereforeeach company's format and structure is generally distinct. However,despite the distinctive structure and format of progs, there are certaintypes of information, generally referred to herein as criticalinformation, that are generally included in every prog. Criticalinformation may be distinguishable or identified by particular elementsin the prog, such as words, characters, symbols, or phrases that aregenerally associated with the particular critical information. Theseidentifying elements generally indicate to one skilled in the drillingart that a particular event, activity, routine, occurrence, or otherhappening, within the drilling operation is being addressed in the prog.The information contained in the prog adjacent to these identifyingelements is likely to pertain to the corresponding event indicated bythe identifying elements (simply by proximity). These correspondingevents may be action items that require some action to be taken toensure that the event is performed according to the prog.

An example of an event for which information is typically included in adrilling operation prog may include a general description of the well tobe drilled. This general description may be considered to be anobjective of the prog. In a drilling operation, other activitiesgenerally detailed in a prog may include operational instructions basedon well depth, spud details, such as the drive pipe depth, cementingdetails, filing of governmental forms, running surface pipe, when toorder more pipe or cement, testing the shoe, intermediate casingcompletion, liner run, reaching total depth, logs to run, notificationsto make, well log samples to deliver, information of interest about theformation, including depths for expected overpressure and depletion,disaster plans, logging run notifications, sample distributions lists,joint service agreements (“JSA's”) for specific tasks, other wellcontrol procedures, directional programs, expected days versus depthdata, etc.

It would be a valuable addition to the field to provide an automatedsystem having a computer system and an action item development engine,where the system would assist an operator to compile and assess adetailed well prog in order to identify potential action items, defineactions to be taken upon encountering the identified action item, anddocument the defined actions in order to trigger automated alerts andreminders to take the actions when a particular action item isencountered. Such a system would enable methods of compiling, assessing,and documenting detailed project plans, including assessing a projectplan for potential action items, defining and documenting actions to betaken upon encountering actual action items, and executing the projectplan, providing alerts and reminders of actions to be taken whenparticular action items are encountered. The response to the alerts andthe actions taken as the result of process could then be recorded versusthe timeline or schedule of the program to close the loop on thecollaboration process.

SUMMARY OF THE DISCLOSURE

Elements included in this disclosure, and their relationships, may beviewed in a variety of ways. As such, the subject matter of the currentdisclosure may be described as a project plan execution system, whereina computer system may be operably coupled with an interface engine, anaction item development engine, and a sensor engine, and the computersystem is capable of receiving and storing a project execution prog andcommunicating with each of the engines to analyze a prog and control awell drilling operation in accordance with the specifications set forthin the prog.

The present disclosure provides a prog analysis and execution system.The system includes a computer control system, an interface engine incommunication with the computer control system, the interface enginebeing configured to receive prog information, and an action itemdevelopment engine in communication with the control system, the actionitem development engine being configured to analyze received proginformation and to determine corresponding action items. The systemfurther includes a sensor engine in communication with the computercontrol system, the sensor engine being configured to receive input fromat least one sensor for use in controlling a well drilling operation,and an operational equipment engine in communication with the computercontrol system, the operational equipment engine being configured toreceive input from the computer control system and to control the welldrilling operation in accordance with the determined action items in theprog.

The present disclosure also provides a computer program embodied on acomputer readable medium, wherein the computer program is configured tocontrol a method for analyzing a prog. The method includes receiving aprog in an interface module, analyzing the prog and determining actionitems corresponding to identified events in the prog in an action itemdevelopment module, and controlling a well drilling operation inaccordance with the determined action items from the prog with an sensormodule and an operational equipment control module.

The present disclosure also provides a method for controlling a welldrilling operation. The method includes receiving a well prog,converting the well prog into a computer readable format, scanning theconverted well prog to identify action items, associating a responsewith each identified action item, and controlling a well drillingoperation in accordance with the responses associated with eachidentified action item from the well prog.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary schematic diagram of a prog facilitationsystem according to one or more aspects of the present disclosure;

FIG. 2 illustrates an exemplary schematic diagram of the components ofan action item development engine according to one or more aspects ofthe present disclosure;

FIG. 3 illustrates an exemplary flow diagram of a process for executinga project using a prog facilitation system according to one or moreaspects of the present disclosure;

FIG. 4 illustrates an exemplary operational display of an action itemidentification module according to one or more aspects of the presentdisclosure; and

FIG. 5 is an illustration of an exemplary operational display of anaction development module according to one or more aspects of thepresent disclosure.

DETAILED DESCRIPTION

Applicant notes that the following description references exemplaryembodiments. The present disclosure, however, is not limited to anyspecifically described embodiment; rather, any combination of thefollowing features and elements, whether related to a describedexemplary embodiment or not, may be used, implemented and/or practicedwithin the scope of the present disclosure. Moreover, in variousexemplary embodiments, the present disclosure may provide advantagesover the prior art; however, although the exemplary embodiments of thepresent disclosure may achieve advantages over other possible solutionsand the prior art, whether a particular advantage is achieved by a givenembodiment is not intended in any way to limit the scope of the presentdisclosure. Thus, the following aspects, features, embodiments andadvantages are intended to be merely illustrative of the presentdisclosure and are not considered elements or limitations of theappended claims; except where explicitly recited in a claim. Similarly,references to “the invention” should neither be construed as ageneralization of any inventive subject matter disclosed herein norconsidered an element or limitation of the appended claims; except whereexplicitly recited in a claim.

Further, at least one embodiment of the present disclosure isimplemented as a program product for use with a computer system. Theprogram product defines functions of the embodiments (including themethods) described herein and can be contained on a variety of computerreadable media. Illustrative computer readable media include, withoutlimitation, (i) information permanently stored on non-writable storagemedia (e.g., read-only memory devices within a computer such as CD-ROMdisks readable by a CD-ROM drive); (ii) alterable information stored onwritable storage media (e.g., floppy disks within a diskette drive orhard-disk drive, writable CD-ROM disks and DVD disks, zip disks, andportable memory devices); and (iii) information conveyed acrosscommunications media, (e.g., a computer, telephone, wired network, orwireless network). These embodiments can include information shared overthe Internet or other computer networks. Such computer readable media,when carrying computer-readable instructions that perform methods of theinvention, represent an exemplary embodiment of the invention.

Further still, in general, software routines implementing embodiments ofthe present disclosure may be part of an operating system or part of aspecific application, component, program, module, object, or sequence ofinstructions, such as an executable script. Such software routinestypically include a plurality of instructions capable of being performedusing a computer system or other type or processor configured to executeinstructions read from a computer readable medium. Also, programstypically include or interface with variables, data structures, etc.that reside in a memory or on storage devices as part of theiroperation. In addition, various programs described herein may beidentified based upon the application for which they are implemented.Those skilled in the art will readily recognize, however, that anyparticular nomenclature or specific application that follows facilitatesa description of the invention and does not limit the invention for usesolely with a specific application or nomenclature. Furthermore, thefunctionality of programs described herein may use a combination ofdiscrete modules or components interacting with one another. Thoseskilled in the art will recognize, however, that different embodimentsmay combine or merge such components and modules in a variety of ways.

Additionally, this disclosure refers to “engines,” which are generallyunderstood in the context of a system to mean an agent, instrument, orcombination of either, or both, agents and instruments that may beassociated to serve a purpose or accomplish a task. Agents andinstruments may include sensors, actuators, switches, relays, valves,power plants, system wiring, equipment linkages, specialized operationalequipment, computers, components of computers, programmable logicdevices, microprocessors, software, software routines, software modules,communication equipment, networks, network services, and other elementsand their equivalents which contribute to the purpose or task to beaccomplished by the engine.

A well prognosis, or a well program, referred to by people in thedrilling industry as a “prog,” or “well prog,” is generally known to bea detailed document containing the information various expertscontribute to plan for and chronicle the steps of drilling a well,which, in general includes all aspects surrounding the creation of anoperational well, including planning, drilling, and completing. The progis used by the operator's company representative, generally known as aCompany-man, to ensure best-practices are used at every step and inevery aspect of drilling the well.

FIG. 1 illustrates a schematic diagram of an exemplary prog facilitationsystem 100 according to one or more aspects of the present disclosure.The exemplary prog facilitation system 100 includes a computer system102 coupled to an interface engine 104, an action item developmentengine 106, a sensor engine 108, and an operational equipment engine110. Each of the engines may be software modules or software routines ina computer program embodied on a computer readable medium, for example.Alternatively, some of the engines may be software modules or routines,while others of the engines may be hardware elements in communicationwith the computer system 102. The computer system 102 operates tocontrol the interaction of data with and between the other components ofthe system 100.

The interface engine 104 includes at least one input and output deviceand system that enables a user to interact with the computer system 102and the functions that the computer system 102 provides. An exemplaryinterface engine 104 may have multiple user stations, which may includea video display, a keyboard, a pointing device, a documentscanning/recognition device, or other device configured to receive aninput from an external source, which may be connected to a softwareprocess operating as part of a computer or local area network. Theexemplary interface engine 104 may include externally positionedequipment configured to input data (such as a well prog) into thecomputer system 102. Data entry may be accomplished through variousforms, including raw data entry, data transfer, or document scanningcoupled with a character recognition process, for example.

The interface engine 104 may include a user station that has a displaywith touch-screen functionality, so that a user may receive informationfrom the system 100, and provide input to the system 100 directly viathe display or touch screen. Other examples of sub-components that maybe part of an interface engine 104 include, but are not limited to,audible alarms, visual alerts, telecommunications equipment, andcomputer-related components, peripherals, and systems. Sub-components ofthe interface engine 104 may be positioned in various locations withinan area of operation, such as on a drilling rig at a drill site.Sub-components of the interface engine 104 may also be remotely locatedaway from the general area of operation, for example, at a businessoffice, at a sub-contractor's office, in an operations manager's mobilephone, and in a sub-contractor's communication linked personal dataappliance. A wide variety of technologies would be suitable forproviding coupling of various sub-components of the interface engine 104and the interface engine 104 itself to the computer system 102.

FIG. 2 illustrates an exemplary schematic diagram of the components ofan action item development engine according to one or more aspects ofthe present disclosure. The action item development engine 106 mayinclude sub-components that may operate to assess or analyze a progentered into the prog facilitation system 100. The action itemdevelopment engine 106 may also operate to assist an operator inassessing the prog. The action item identification module 202 generallyfunctions to review the prog according to a predetermined logic programconfigured to identify events from elements in the prog and determine ifthe event requires some action on the part of the system or an operatorthat would make the event an action item. The action item identificationmodule 202 may work either in conjunction with the operator, orindependently, to identify potential events and determine if thosepotential events are action items. Thus, an exemplary embodiment of thepresent disclosure, the action item identification module 102 generallyoperates to scan through a prog to identify relevant events. Therelevant events to be identified may be predetermined and may be locatedin the prog by key word, symbol, phrase, etc. searching. Once apotential event is identified, the action item identification module 202marks a representative section of data for the potential event, so thatthe section of data may be readily identified for future consideration.A suitable form of marking may include highlighting a section of textthat identifies the potential event or digitally marking an electronicversion of the prog.

For each potential event identified, the action item development module202 then makes a determination of whether the potential event is anaction item. The determination of which events constitute action itemsmay be conducted by a software routine configured to analyze the eventsin accordance with a predetermined algorithm. The software program maybe configured to compare identified events or portions of events to aknown database of events that are known to constitute action items todetermine if the identified event should be an action item in thecurrent prog. For each action item identified, the action developmentmodule 204 operates to determine what action to take in response to theoccurrence of the identified action item, where the action to be takenmay be detailed to include what action to take, who is responsible totake the action, when to take the action, how and to whom to confirm theaction is taken, and any other action the operator deems necessary andprudent to have performed at the occurrence of the action item. Thedetailed actions may be saved as part of the prog (integrally) in a formuseable by the prog facilitation system 100 during execution of theprog, so that the prog facilitation system 100 may prompt appropriateparties to take action at the appropriate time, as defined in the progand action items. Alternatively, a separate report or action item listmay be created for use by an operator.

In an exemplary embodiment of the present disclosure, a computer systemmay perform the task of action item identification module 202, toefficiently identify related information that may be inferred from text.A computer system that may perform the functions of an action itemidentification module 202 may employ technology referred to as LatentSemantic Indexing (“LSI”). LSI technology is described, for example, inU.S. Pat. No. 4,839,853, issued Jun. 13, 1989, to Deerwester, S, et al.,entitled “Computer Information Retrieval Using Latent SemanticStructure.” Additionally, a computer system that may perform functionsof an action item identification module 202 may employ LSI technology incross-language applications as described, for example, in U.S. Pat. No.5,301,109, issued Apr. 5, 1994, to Landauer, T., et al., entitled“Computerized Cross-language Document Retrieval Using Latent SemanticIndexing.” Additionally, a exemplary computer system that may performfunctions of an action item identification module 202 may employ the LSItechnology in text analysis and interpretation as described, forexample, in U.S. Patent Application No. 20020026456, filed Aug. 24,2001, by Bradford, R., entitled “Word Sense Disambiguation,” U.S. PatentApplication No. 200220103799, filed Aug. 2, 2002, to Bradford, R., etal., entitled “Method for Document Comparison and Selection,” and U.S.patent application Ser. No. 10/337,426, filed Jan. 7, 2003, also byBradford, R., entitled “Vector Space Method for Secure InformationSharing.” Each of the above noted references is hereby incorporated byreference into the present application, to the extent that thesereferences are not inconsistent with the present disclosure.

Referring back to FIG. 1, the sensor engine 108 may include devices suchas sensors, meters, detectors, or other devices configured to measure orsense a parameter related to a prog specification or a component of awell drilling operation. The sensors or other detection devices aregenerally configured to sense or detect activity, conditions, andcircumstances in an area to which the device has access. Sub-componentsof the sensor engine 108 may be deployed at any operational area whereinformation on the execution of the prog may occur. Readings from thesensor engine 108 are fed back to the computer system 102. The computersystem 102 may send signals to the sensor engine 108 to adjust thecalibration or operational parameters in accordance with a controlprogram in the computer system, which is generally based upon the prog.Additionally, the computer system 102 may generate outputs that controlthe well drilling operation, as discussed below.

The operational equipment engine 110 may include a plurality of devicesconfigured to facilitate accomplishment of the objectives set forth inthe prog. In an exemplary embodiment, the objective is to drill a wellin accordance with the specifications set forth in the prog. Therefore,the operational equipment engine 110 may include hydraulic rams, rotarydrives, valves, and pumps, control systems, and any other tools,machines, equipment, etc. that would be required to drill the well inaccordance with the prog. The operational equipment engine 110 may bedesigned to exchange communication with computer system 102, so as tonot only receive instructions, but to provide information on theoperation of operational equipment engine 110 apart from any associatedsensor engine 108. The operational equipment engine 110 may beconfigured to receive control inputs from the computer system 102 and tocontrol the well drilling operation (the components conducting the welldrilling operation) in accordance with the received inputs from thecomputer system 102.

Referring now to FIGS. 3-5, the process of an exemplary well progfacilitation process 300 is illustrated. The exemplary well progdrilling facilitation process 300 begins at 302. An exemplary projectexecution prog is entered into a computer system 102, at 310, throughinterface engine 104. Interface engine 104 may include equipment andsystems that support a variety of prog data entry methods. Entering theproject execution prog may be accomplished by a selected manner orcombination of manners, which include copying a text data file into thecomputer system, at 3102, scanning a document into the computer systemand conducting a character recognition process on the document at 3104,responding to an interview that asks pertinent questions about the fullrange of potential operations the prog may cover (initiated by thefacilitation module) at 3106, or incorporating the prog or elements ofthe prog into the computer system 102 by any other method oftransferring text from a hard copy document into a machine readableformat at 3108.

Typical activities that will be described in a project execution proginclude any activity understood to one skilled in the art to relate toexecution of the project (drilling the well). In a drilling operation,such activities may include operational instructions based on welldepth, spud details, such as the drive pipe depth, cementing details,and filing of governmental forms, running surface pipe, including orderthe pipe, ordering the cement, and testing the shoe, intermediate casingcompletion, liner run, reaching total depth, including logs to run,notifications to make, well log samples to deliver, information ofinterest about the formation, including depths for expected overpressureand depletion, disaster plans, logging run notifications, sampledistributions lists, JSA's for specific tasks, other well controlprocedures, directional programs, and expected days versus depth data.An exemplary prog excerpt 400 is shown in FIG. 4, which illustrates theplurality of details and specifications that may be contained in a prog.

Once the exemplary project execution prog is entered into a computersystem 102, at 310, the exemplary facilitation module 300 initiates aprocess of scanning or assessing the prog for events and action items at320. In the exemplary facilitation process 300, potential events thatmay occur during execution of the prog are identified and assessed bythe action item development engine 106 to determine if the operatorneeds any action to be conducted in response to the event in the prog.An operator, through the computer system 102 and the interface engine104, may indicate that an action is to be taken (or omitted) inaccordance with the information presented in the prog, interactively andthrough defined instructions, whether the action item identificationmodule 202 should identify a particular event as an action item, or not.

In one embodiment of the present disclosure, the entire prog is scannedor assessed by the action item identification module 202, to identifypotential action items, at 3202, and the action item identificationmodule 202 marks a representative section of data in the prog for eachidentified action item, so that each action item may be readilyidentified for future consideration. A suitable form of marking mayinclude highlighting a section of text that identifies the action item,or electronically marking a section of the prog in the situation wherethe prog has been converted to an electronic format for assessment.Potential action items 410 are shown as shaded areas in FIG. 4.

Once the action item identification module 202 identifies the actionitems if the prog in 3202, the action development module 204 may useinstructions from an operator to define actions that should be takenupon the occurrence of each particular action item. Alternatively, theaction development module 204 may be configured to determine appropriateactions in response to action items without external interaction. Forexample, the action development module 204 may include a softwareroutine configured to identify particular action items and associate theidentified action items with a particular predefined action to be takenin response to the action item. The action development module 204 isconfigured to locate and select a potential action item, at 3204. In theexemplary embodiment, a potential action item is located by the operatornoticing the potential action item is marked, and then selecting themarked potential action item with the cursor 420 of the interface engine104. In the exemplary embodiment, right-clicking on the potential actionitem 410 activates definition entry, at 3206, causing a menu 430 toappear. As noted above, in an alternative to having an operator selectactions in response to identified action items, the action developmentmodule 204 may be configured to autonomously determine the appropriateactions in response to the identified actions items in at least oneembodiment of the present disclosure. This autonomous determination maybe driven by a software routine configured to compare identified actionitems to a database of known actions in response to action items.

The menu 430 may offer standard word processing action choices 432, aswell as a define action choice 434, and a clear action choice 436. In3208, the define action choice 434 is selected, which opens actiondefinition window 500, which permits documentation of various actionsthe operator wants taken upon the occurrence of the particular actionitem. The exemplary action definition window 500 has an action item box510, an occurrence window 520, an action documentation window, and analert distribution window 540. Action item box 510 may have aninstruction box 512 and an item box 514. The exemplary instruction box512 accepts an entry of an instruction for someone to carry-out, such asexpect, set, run, and alert. The exemplary item box 514 accepts an entryof the item to which the instruction in instruction box 512 relates.Examples of entries that may be made in the item box 514 includeformation top, pipe, logs, and personnel.

Occurrence window 520 may have a parameter box 522 and a specificationbox 524. The exemplary parameter box 522 accepts an entry of a physicalparameter that my be encountered or achieved during the operation, suchas a measured depth (“MD”), a true vertical depth (“TVD”), and avertical section (“VS”). The exemplary specification box 524 may acceptan entry of quantifiable values of the entry in the parameter box 522,which may be used to know that physical parameter should be encounteredwhen the specified quantifiable value is attained. Examples ofquantifiable values include a depth measurement, typically in feet, adate, and a time, and may be entered in the specification box 524singularly or in combinations.

Action documentation window 530 may have a set of selection boxes 532,with corresponding potential entries 534, as well as a comment box 536.Selection boxes 532 may be clicked to change the selection box 532 tocontain a mark, in order to indicate the selection box 532 is selected.In an exemplary embodiment, a selection box 532 may correspond to achoice to add comments to a log upon the occurrence of the particularaction item. Other selection boxes 532 may indicate what potentialentries the operator of the facilitation module 300 wants entered intothe log. An additional select box permits the operator of thefacilitation module 300 to choose a text entry, entered in the commentbox 536, is to be entered into the log upon the occurrence of theparticular action item.

An alert distribution window 540 may have a set of selection boxes 543,with corresponding potential recipients 544, as well as custom contactinput boxes 546, and a response instruction box 548. Selection boxes 542may be clicked to change the selection box 542 to contain a mark, inorder to indicate the selection box 542 is selected. In the exemplaryembodiment, a selection box 542 corresponds to a choice to providealerts upon the occurrence of the particular action item. Otherselection boxes 542 indicate the designation of the correspondingrecipient 544 to receive the alert upon the occurrence of the particularaction item. Custom contact input boxes 546 permits the operator of thefacilitation module 300 to identify, and provide appropriate contactinformation, for other recipients not anticipated in the list ofrecipients 544. Exemplary entries in to custom contact input boxes 546include email addresses, fax numbers, and pager numbers. A customcontact input box 546 may accept information to reach multiplerecipients, such as a string of delineated email addresses, adesignation of an email mailing list, or a fax or pager distributionlist. Response instruction 548 permits the operator of the facilitationmodule 300 to require recipients acknowledge receipt of the alert. Thismay be accomplished by varied methods, depending on the manner in whichthe alert is distributed. Protocols may be established and disseminatedto users that define what makes for an appropriate response to aresponse instruction 548 that requires an acknowledgement. Additionally,a response instruction 548, and corresponding selection box 542, may beassociated with each recipient 544, such that selected recipients 544may be required to acknowledge an alert, while other recipients 544 maynot be required.

The action definition is then saved, at 3210. The action developmentmodule 204 then tests to see if the action development engine 106 hasreached the end of the prog, where all the potential action item 410 inthe prog have been reviewed, at 3212. If the end of the prog is notreached, the action development module 204 selects another potentialaction item 410, at 3204. If the end of the prog is reached, at 3212,the exemplary facilitation module 300 is in a state where the actiondefinitions may be employed to execute the prog, at 330.

During execution of the prog, at 330, data from the sensor engine 108allows the computer system to detect the occurrence of an action item,at 3302. Upon detection of an action item, at 3302, the exemplaryfacilitation module 300 follows the action definition and takes theplanned action, at 3304. After all the planned action for a particularaction item is taken the facilitation module 300 tests to see if the endof the prog has been reached, at 3306. If the end of the prog is notreached, the facilitation module 300 continues to monitor the data fromthe sensor engine 108, waiting for the detection of the next action itemoccurrence, at 3302. If the end of the prog is reached, at 3306, thefacilitation module 300 concludes, at 3308.

In an alternate exemplary embodiment of assessing the prog, at 320, oncethe action item identification module 202 identifies an action item, theaction development module 204 employs instructions from an operator todefine actions that should be taken upon the occurrence of thatparticular action item.

In an additional alternate exemplary embodiment of assessing the prog,at 320, the action item identification module 202 compiles a list ofpotential action items 410 apart from the text of the prog, at 3202. Inthis embodiment, the potential action items 410 may appear in a listform, rather than contained in the text of the prog. The potentialaction items 410 may then be either cleared from the list, as not beingactual action items, or they may be defined from the list in a similarfashion as described above, at 3204 through 3212.

Although only a few exemplary embodiments have been described in detailabove, those skilled in the art will readily appreciate that manymodifications are possible in the exemplary embodiments withoutmaterially departing from the novel teachings and advantages of thisdisclosure. Accordingly, all such adjustments and alternatives areintended to be included within the scope of the present disclosure, asdefined exclusively in the following claims. Those skilled in the artshould also realize that such modifications and equivalent constructionsor methods do not depart from the spirit and scope of the presentdisclosure, and that they may make various changes, substitutions, andalternations herein without departing from the spirit and scope of thepresent disclosure. Additionally, the inventors contemplate that anycombination of the above noted exemplary embodiments may be used, as theinvention is not limited to any particular combination of the abovenoted exemplary embodiments.

1-21. (canceled)
 22. A transferable well prog system, comprising:operational instructions based on a plurality of parameters for at leastone well; a logging system adapted to receive critical informationindicative of a particular event for the at least one well within aparticular geologic region; a database of events that constitute actionitems that require at least one procedure to be taken; wherein the wellprog system from at least one well drilling operation is transferable toat least one other well.
 23. The transferable well prog system of claim22, wherein the particular event comprises an activity, a routine, anoccurrence, or an action item.
 24. The transferable well prog system ofclaim 22, further comprising one or more notifications that alert orremind a corresponding operator when a particular action needs to betaken during a drilling operation.
 25. The transferable well prog systemof claim 24, wherein the recipient(s) of each notification is requiredto respond before the drilling operation proceeds.
 26. The transferablewell prog system of claim 22, further comprising at least one inputsource to enter data into the well prog system or components thereof.27. The transferable well prog system of claim 22, wherein the pluralityof parameters comprise: well depth, a spud detail, a cementing detail,filing of a governmental form, running surface pipe, ordering pipe,ordering cement, testing a shoe, intermediate casing completion, linerrun, reaching total depth, a log to run, a notification to make, a welllog sample to deliver, information of interest about the formation, adisaster plan, joint service agreements for specific tasks, a wellcontrol procedure, logging run notification, a sample distribution list,a directional program, and expected days versus depth data.
 28. Thetransferable well prog system of claim 22, wherein the database ofaction items is adapted to have additional newly encountered actionitems added during the drilling process.
 29. The transferable well progsystem of claim 22, wherein the well prog system is searchable.
 30. Thetransferable well prog system of claim 22, wherein the operator can addcomments to the logging system.
 31. The transferable well prog system ofclaim 22, wherein the at least one other well is adjacent to thegeologic region.
 32. The transferable well prog system of claim 22,wherein the logging system includes information from a sensor engineconfigured to measure or sense a parameter related to a component of awell drilling operation.
 33. A method for controlling a well drillingoperation, comprising: receiving a well prog; assessing the well andadjusting the well prog regarding one or more parameters relative to apreviously drilled well; assessing the well prog to identify each actionitem; associating a response with each identified action item; storingthe action items within the well prog; controlling a well drillingoperation in accordance with the response associated with eachidentified action item; and updating the well prog for drilling afurther well by adding to the well prog one or more additional eventsthat arise during the well drilling operation.
 34. The method of claim33, wherein assessing the well prog to identify each action itemcomprises comparing a plurality of potential action items to a databaseof action items, and marking the data corresponding to the potentialaction items for later analysis.
 35. The method of claim 33, wherein theone or more parameters relative to a previously drilled well areautomatically acted upon when the well prog system is transferred to awell within the same geologic region.
 36. The method of claim 33,wherein associating a response with each identified action itemcomprises matching identified action items with corresponding responsesin a database of predetermined responses.
 37. The method of claim 33,wherein associating a response with each identified action itemcomprises the operator selecting the response from a list of possibleresponses presented to the operator on a screen.
 38. The method of claim33, wherein the further well is within the same geologic region as aprior well that used the same method.
 39. The method of claim 38,further comprising storing the physical parameters of the prior wellwithin the well prog system.
 40. The method of claim 33, furthercomprising inputting operational instructions into a well prog systemafter assessing the well to identify newly encountered physicalparameters within the well.
 41. The method of claim 40, wherein theoperational instructions are automatically calibrated based on physicalparameters of the well.
 42. The method of claim 33, wherein the well andwell prog system are assessed during execution of the well prog.
 43. Themethod of claim 33, wherein assessing the well and adjusting the wellprog regarding one or more parameters relative to a previously drilledwell comprises using a sensor engine to detect a condition orcircumstance within the area of operation of the well.